Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference
467-tree-1
name
1662
tree-preservation-order

undefined

467-tpo-1
uprn
address-text
point
POINT (-1.023787 50.882863)
geometry
MULTIPOLYGON (((-1.023660 50.882849,-1.023665 50.882875,-1.023683 50.882897,-1.023711 50.882915,-1.023746 50.882927,-1.023786 50.882931,-1.023826 50.882928,-1.023861 50.882917,-1.023890 50.882899,-1.023909 50.882877,-1.023916 50.882852,-1.023910 50.882827,-1.023892 50.882804,-1.023864 50.882786,-1.023829 50.882774,-1.023789 50.882770,-1.023750 50.882773,-1.023714 50.882784,-1.023685 50.882802,-1.023666 50.882825,-1.023660 50.882849)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL